Systems and methods for identifying service type of data usage on 5g new radio (nr) radio access technology type

ABSTRACT

Aspects of the subject disclosure may include, for example, obtaining a message associated with a 5th Generation (5G) wireless service, the message containing: a first section including a service type identifier entry and a first timestamp that corresponds to the service type identifier entry; and a second section including a secondary radio access technology (RAT) entry, one or more data volume entries, and a second timestamp that corresponds to the secondary RAT entry and to the one or more data volume entries; matching the first timestamp and the second timestamp based upon a first value of the first timestamp equaling a second value of the second timestamp; and responsive to the matching of the first timestamp and the second timestamp, associating the service type identifier entry of the first section with the one or more data volume entries of the second section. Other embodiments are disclosed.

FIELD OF THE DISCLOSURE

The subject disclosure relates to systems and methods for identifying service type of data usage on 5^(th) Generation (5G) New Radio (NR) Radio Access Technology Type. In one specific example, the subject disclosure relates to identifying service type for 5G “Option 3X” data usage on the NR Radio Access Technology (RAT) Type.

BACKGROUND

In 5G Option 3X, all data usage is reported as having radio access technology (RAT) Type=EUTRAN (LTE) regardless of whether some or all of the data usage was actually via 5G NR frequency spectrum. This is due to the nature of Option 3X, in which the LTE eNodeB is the master node and the 5G NR gNodeB is the secondary node. Such a configuration traditionally makes it impossible to identify the serving network based on the RAT Type parameter in a packet data network gateway (PGW) or serving gateway (SGW) charging data record (CDR). The only way currently available under 3GPP standards for identification of NR data usage volume is Secondary RAT Usage Data Reporting. Secondary RAT Usage Data Reporting (defined in 3GPP TS 23.401 Release 15) includes access type NR and usage data reporting for the Secondary RAT, in this case NR. Such Secondary RAT Usage Data Reporting includes reporting of the combination of NR usage as defined in 3GPP TS 37.340. The serving gateway (SGW) sends the data volume reports on to the packet data network (PDN) gateways (PGW) identified in bilateral roaming agreements and/or in the same network (Home user case). Due to limitations in Standards and vendor implementations, this NR as Secondary RAT usage data is traditionally only useful for wholesale billing and high-level network usage reporting. Such NR as Secondary RAT usage data is traditionally not useful for retail billing because service ID's cannot be directly applied by the PGW (service ID's are used to inform billing systems what type of data the device is using so that the data usage can be differentiated; as a result of not directly having a service ID available, there is traditionally no way to identify data which should be zero-rated versus billable usage to the subscriber).

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 is a block diagram illustrating an example, non-limiting embodiment of a communication network in accordance with various aspects described herein.

FIG. 2A is a block diagram illustrating an example, non-limiting embodiment of a network call flow (that can function, for example, within the communication network of FIG. 1) in accordance with various aspects described herein.

FIG. 2B depicts an illustrative embodiment of a method in accordance with various aspects described herein.

FIG. 2C depicts an illustrative embodiment of a method in accordance with various aspects described herein.

FIG. 2D depicts an illustrative embodiment of a method in accordance with various aspects described herein.

FIG. 3 is a block diagram illustrating an example, non-limiting embodiment of a virtualized communication network in accordance with various aspects described herein.

FIG. 4 is a block diagram of an example, non-limiting embodiment of a computing environment in accordance with various aspects described herein.

FIG. 5 is a block diagram of an example, non-limiting embodiment of a mobile network platform in accordance with various aspects described herein.

FIG. 6 is a block diagram of an example, non-limiting embodiment of a communication device in accordance with various aspects described herein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrative embodiments for customer billing related to wireless usage (e.g., retail customer billing related to usage of one or more wireless frequencies (or usage of one or more wireless frequency ranges)). Other embodiments are described in the subject disclosure.

One or more aspects of the subject disclosure include mechanisms to facilitate determination (such as by a wireless operator or carrier) of not only how much data was used on the New Radio (NR) RAT, but also the type of data that was transmitted (and/or received) based on the service ID. In one example, this distinction can be beneficial in facilitating application of differentiated retail billing rates. In another example, the distinction can be beneficial in helping the wireless operator or carrier understand not only how much data is being used on NR spectrum versus LTE but also the nature of the application(s) being used by each subscriber. The additional granularity provided by various embodiments can also be used in contract terms with, for example, IPX (GSMA IP Packet Exchange) transport providers where certain types of 5G data usage are billed at a different rate than other packet data. The additional granularity provided by various embodiments can also be beneficial in troubleshooting customer issues.

One or more aspects of the subject disclosure include receiving a message (e.g., a charging data record (CDR)) and processing the data in the CDR to determine for a given customer (e.g., a wireless subscriber) a service type and/or a data usage (e.g., an uplink data volume of a 5G service and/or a downlink data volume of a 5G service).

One or more aspects of the subject disclosure include generating a message (e.g., a charging data record (CDR)) to indicate for a given customer (e.g., a wireless subscriber) a service type and/or a data usage (e.g., an uplink data volume of a 5G service and/or a downlink data volume of a 5G service).

Referring now to FIG. 1, a block diagram is shown illustrating an example, non-limiting embodiment of a communication network 100 in accordance with various aspects described herein. For example, communication network 100 can facilitate in whole or in part message processing (e.g., CDR processing), message post-processing (e.g., CDR post-processing), message creation (e.g., CDR creation) and/or billing that is related to wireless frequency usage. In particular, a communications network 125 is presented for providing broadband access 110 to a plurality of data terminals 114 via access terminal 112, wireless access 120 to a plurality of mobile devices 124 and vehicle 126 via base station or access point 122, voice access 130 to a plurality of telephony devices 134, via switching device 132 and/or media access 140 to a plurality of audio/video display devices 144 via media terminal 142. In addition, communication network 125 is coupled to one or more content sources 175 of audio, video, graphics, text and/or other media. While broadband access 110, wireless access 120, voice access 130 and media access 140 are shown separately, one or more of these forms of access can be combined to provide multiple access services to a single client device (e.g., mobile devices 124 can receive media content via media terminal 142, data terminal 114 can be provided voice access via switching device 132, and so on).

The communications network 125 includes a plurality of network elements (NE) 150, 152, 154, 156, etc. for facilitating the broadband access 110, wireless access 120, voice access 130, media access 140 and/or the distribution of content from content sources 175. The communications network 125 can include a circuit switched or packet switched network, a voice over Internet protocol (VoIP) network, Internet protocol (IP) network, a cable network, a passive or active optical network, a 4G, 5G, or higher generation wireless access network, WIMAX network, UltraWideband network, personal area network or other wireless access network, a broadcast satellite network and/or other communications network.

In various embodiments, the access terminal 112 can include a digital subscriber line access multiplexer (DSLAM), cable modem termination system (CMTS), optical line terminal (OLT) and/or other access terminal. The data terminals 114 can include personal computers, laptop computers, netbook computers, tablets or other computing devices along with digital subscriber line (DSL) modems, data over coax service interface specification (DOCSIS) modems or other cable modems, a wireless modem such as a 4G, 5G, or higher generation modem, an optical modem and/or other access devices.

In various embodiments, the base station or access point 122 can include a 4G, 5G, or higher generation base station, an access point that operates via an 802.11 standard such as 802.11n, 802.11ac or other wireless access terminal. The mobile devices 124 can include mobile phones, e-readers, tablets, phablets, wireless modems, and/or other mobile computing devices.

In various embodiments, the switching device 132 can include a private branch exchange or central office switch, a media services gateway, VoIP gateway or other gateway device and/or other switching device. The telephony devices 134 can include traditional telephones (with or without a terminal adapter), VoIP telephones and/or other telephony devices.

In various embodiments, the media terminal 142 can include a cable head-end or other TV head-end, a satellite receiver, gateway or other media terminal 142. The display devices 144 can include televisions with or without a set top box, personal computers and/or other display devices.

In various embodiments, the content sources 175 include broadcast television and radio sources, video on demand platforms and streaming video and audio services platforms, one or more content data networks, data servers, web servers and other content servers, and/or other sources of media.

In various embodiments, the communications network 125 can include wired, optical and/or wireless links and the network elements 150, 152, 154, 156, etc. can include service switching points, signal transfer points, service control points, network gateways, media distribution hubs, servers, firewalls, routers, edge devices, switches and other network nodes for routing and controlling communications traffic over wired, optical and wireless links as part of the Internet and other public networks as well as one or more private networks, for managing subscriber access, for billing and network management and for supporting other network functions.

Referring now to FIG. 2A, this is a block diagram illustrating an example, non-limiting embodiment of a network call flow 200 (that can function, for example, within the communication network of FIG. 1) in accordance with various aspects described herein. As seen, the network call flow 200 can involve eNodeB 202, mobility management entity (MME) 204, serving gateway (SGW) 206, and packet data network gateway (PGW) 208.

Still referring to FIG. 2A, it is noted that the SGW 206 and the PGW 208 support receiving uplink and downlink data volumes reported per bearer for the secondary NR RAT. Further, the SGW 206 and PGW 208 support “change notification request/acknowledgement” on S11 and S5. In operation, the RAN reports the Secondary RAT usage data (such as to the mobility management entity (MME)) and the mobility management entity 204 will send the volume reports that are received from the eNodeB 202 to the SGW 206 in a “Change Notification Request” (see arrow “1” in FIG. 2A). The SGW 206 processes the received “Change Notification Request” and forwards this information in another “Change Notification Request” (see arrow “2” in FIG. 2A) to PGW 208 if the SGW 206 receives the Secondary RAT Usage Data Report with the IRPGW flag set to “1” from the mobility management entity 204 (of note, the SGW 206 and the PGW 208 support receiving and processing NR data volume information from the mobility management entity during X2 handover, S1 handover, S1 Release, E-RAB modification, bearer and session deactivation). See, also, the change notification acknowledgements (of receipt) at arrows “3” and “4”). In addition, the SGW 206 and the PGW 208 generate CDRs including Secondary RAT Usage Report.

Referring now to an example of one embodiment, a correlation between the standard 3GPP data usage reported in the PGW CDR and the Secondary RAT usage reports is used to identify the Service ID of the NR usage in post-processing. This correlation can be done based on timestamps in the CDR containers for the individual usage containers/entries. Below is one specific example (according to an embodiment) showing a portion of a PGW CDR from a test (the order of entries in the listOfRANSecondaryRATUsageReports (see the left-hand column, number 02238597, which is shown in bold below) is organized in the CDR to coincide with the order of entries in the listOfServiceData entries (see the left-hand column, number 02237017, which is shown in bold below). The corresponding entries are shown below from both lists in connection with a common timestamp of “10:30:27” (see the left-hand column, numbers 02237266, 02238691, which are shown in bold below). Note that certain values in the below example have been replaced with “- - - -” markings.

Record #7009 02236826: bf 4f 82 09 12 pGWRecord (2322 bytes): 02236831: 80 01 55 |--recordType (1 byte) = 85 (PGWRecord) 02236834: ---- >|--servedIMSI (8 bytes) = ---- 02236844: a4 06 |--p-GWAddress (6 bytes): 02236846: ---- |--|--iPBinV4Address (4 bytes) = ---- 02236852: 85 03 0e 00 0d |--chargingID (3 bytes) = 917517 02236857: a6 06 |--servingNodeAddress (6 bytes): 02236859: ---- |--|--iPBinV4Address (4 bytes) = ---- 02236865: ---- >|--accessPointNameNI (20 bytes) = “----” 02236887: 88 02 f1 8d |--pdpPDNType (2 bytes) = f18d 02236891: a9 14 |--servedPDPAddress (20 bytes): 02236893: a0 12 |--|--iPAddress (18 bytes): 02236895: ---- >|--|--|--iPBinV6Address (16 bytes) = ---- 02236913: 8b 01 ff |--dynamicAddressFlag (1 byte) = −1 02236916: 8d 09 19 09 18 10 >|--recordOpeningTime (9 bytes) = 19/09/18 10:27:24 −07:00 02236927: 8e 02 03 d9 |--duration (2 bytes) = 985 02236931: 8f 01 13 |--causeForRecClosing (1 byte) = 19 (maxChangeCond) 02236934: 91 01 02 |--recordSequenceNumber (1 byte) = 2 02236937: ---- >|--nodeID (17 bytes) = “----” 02236956: 94 01 29 |--localSequenceNumber (1 byte) = 41 02236959: 95 01 00 |--apnSelectionMode (1 byte) = 0 (mSorNetworkProvidedSubscriptionVerified) 02236962: ---- >|--servedMSISDN (7 bytes) = ---- 02236971: 97 02 00 00 |--chargingCharacteristics (2 bytes) = 0000 02236975: 98 01 03 |--chChSelectionMode (1 byte) = 3 (homeDefault) 02236978: ---- |--servingNodePLMNIdentifier (3 bytes) = ---- 02236983: ---- >|--servedIMEISV (8 bytes) = ---- 02236993: 9e 01 06 |--rATType (1 byte) = 6 (6 = EUTRAN) 02236996: 9f 1f 02 8a 01 |--mSTimeZone (2 bytes) = 8a01 02237001: ---- >|--userLocationInformation (13 bytes) = ---- (uliLac=, uliCellId=----, uliTac=----, uliEcgi=----) 02237017: bf 22 82 06 21 |--listOfServiceData (1569 bytes): 02237022: 30 64 |--|--SEQUENCE (100 bytes): 02237024: 81 04 01 60 00 80 |--|--|--ratingGroup (4 bytes) = 23068800 02237030: ---- |--|--|--chargingRuleBaseName (3 bytes) = “----” 02237035: 84 01 15 |--|--|--localSequenceNumber (1 byte) = 21 02237038: 85 09 19 09 18 10 >|--|--|--timeOfFirstUsage (9 bytes) = 19/09/18 10:27:41 −07:00 02237049: 86 09 19 09 18 10 >|--|--|--timeOfLastUsage (9 bytes) = 19/09/18 10:27:41 −07:00 02237060: 87 01 00 |--|--|--timeUsage (1 byte) = 0 02237063: 88 05 00 00 00 00 >|--|--|--serviceConditionChange (5 bytes) = 0000.0000 0000.0000 0000.0000 0000.0000 1000.0000 02237070: 89 16 70 08 00 00 >|--|--|--qoSInformationNeg (22 bytes) = 70080000000000000000000000000000000000000000 02237094: aa 06 |--|--|--sgsn-Address (6 bytes): 02237096: ---- |--|--|--iPBinV4Address (4 bytes) = ---- 02237102: 8c 02 00 b3 |--|--|--datavolumeFBCUplink (2 bytes) = 179 02237106: 8d 02 00 b1 |--|--|--datavolumeFBCDownlink (2 bytes) = 177 02237110: 8e 09 19 09 18 10 >|--|--|--timeOfReport (9 bytes) = 19/09/18 10:27:52 −07:00 02237121: 91 01 01 |--|--|--serviceIdentifier (1 byte) = 1 02237124: 30 4c |--|--SEQUENCE (76 bytes): 02237126: 81 04 01 60 00 80 |--|--|--ratingGroup (4 bytes) = 23068800 02237132: ---- |--|--|--chargingRuleBaseName (3 bytes) = “----” 02237137:84 01 16 |--|--|--localSequenceNumber (1 byte) = 22 02237140: 85 09 19 09 18 10 >|--|--|--timeOfFirstUsage (9 bytes) = 19/09/18 10:28:29 −07:00 02237151: 86 09 19 09 18 10 >|--|--|--timeOfLastUsage (9 bytes) = 19/09/18 10:28:31 −07:00 02237162: 87 01 02 |--|--|--timeUsage (1 byte) = 2 02237165: 88 05 00 00 00 00 >|--|--|--serviceConditionChange (5 bytes) = 0000.0000 0000.0000 0000.0000 0000.0000 1000.0000 02237172: aa 06 |--|--|--sgsn-Address (6 bytes): 02237174: ---- |--|--|--|--iPBinV4Address (4 bytes) = ---- 02237180: 8c 02 03 98 |--|--|--datavolumeFBCUplink (2 bytes) = 920 02237184: 8d 02 03 dc |--|--|--datavolumeFBCDownlink (2 bytes) = 988 02237188: 8e 09 19 09 18 10 >|--|--|--timeOfReport (9 bytes) = 19/09/18 10:28:41 −07:00 02237199: 91 01 01 |--|--|--serviceIdentifier (1 byte) = 1 02237202: 30 4c |--|--SEQUENCE (76 bytes): 02237204: 81 04 01 60 00 80 |--|--|--ratingGroup (4 bytes) = 23068800 02237210: ---- |--|--|--chargingRuleBaseName (3 bytes) = “----” 02237215: 84 01 17 |--|--|--localSequenceNumber (1 byte) = 23 02237218: 85 09 19 09 18 10 >|--|--|--timeOfFirstUsage (9 bytes) = 19/09/18 10:29:07 −07:00 02237229: 86 09 19 09 18 10 >|--|--|--timeOfLastUsage (9 bytes) = 19/09/18 10:30:17 −07:00 02237240: 87 01 46 |--|--|--timeUsage (1 byte) = 70 02237243: 88 05 00 00 00 00 >|--|--|--serviceConditionChange (5 bytes) = 0000.0000 0000.0000 0000.0000 0000.0000 1000.0000 02237250: aa 06 |--|--|--sgsn-Address (6 bytes): 02237252: ---- |--|--|--|--iPBinV4Address (4 bytes) = ---- 02237258: 8c 02 15 b4 |--|--|--datavolumeFBCUplink (2 bytes) = 5556 02237262: 8d 02 16 fa |--|--|--datavolumeFBCDownlink (2 bytes) = 5882 02237266: 8e 09 19 09 18 10 >|--|--|--timeOfReport (9 bytes) = 19/09/18 10:30:27 −07:00 02237277: 91 01 01 |--|--|--serviceidentifier (1 byte) = 1 02237280: 30 4c |--|--SEQUENCE (76 bytes): 02237282: 81 04 01 60 00 80 |--|--|--ratingGroup (4 bytes) = 23068800 02237288: ---- |--|--|--chargingRuleBaseName (3 bytes) = “----” 02237293: 84 01 18 |--|--|--localSequenceNumber (1 byte) = 24 02237296: 85 09 19 09 18 10 >|--|--|--timeOfFirstUsage (9 bytes) = 19/09/18 10:30:37 −07:00 02237307: 86 09 19 09 18 10 >|--|--|--timeOfLastUsage (9 bytes) = 19/09/18 10:30:37 −07:00 02237318: 87 01 00 |--|--|--timeUsage (1 byte) = 0 02237321: 88 05 00 00 00 00 >|--|--|--serviceConditionChange (5 bytes) = 0000.0000 0000.0000 0000.0000 0000.0000 1000.0000 02237328: aa 06 |--|--|--sgsn-Address (6 bytes): 02237330: ---- |--|--|--|--iPBinV4Address (4 bytes) = ---- 02237336: 8c 02 05 ce |--|--|--datavolumeFBCUplink (2 bytes) = 1486 02237340: 8d 02 03 94 |--|--|--datavolumeFBCDownlink (2 bytes) = 916 02237344: 8e 09 19 09 18 10 >|--|--|--timeOfReport (9 bytes) = 19/09/18 10:30:48 −07:00 02237355: 91 01 01 |--|--|--serviceidentifier (1 byte) = 1 . . . . . 02238597: bf 49 82 02 27 |--listOfRANSecondaryRATUsageReports (551 bytes): 02238602: 30 1f |--|--SEQUENCE (31 bytes): 02238604: 81 01 00 |--|--|--dataVolumeUplink (1 byte) = 0 02238607: 82 01 00 |--|--|--dataVolumeDownlink (1 byte) = 0 02238610: 83 09 19 09 18 10 >|--|--|--rANStartTime (9 bytes) = 19/09/18 10:27:41 −07:00 02238621: 84 09 19 09 18 10 >|--|--|--rANEndTime (9 bytes) = 19/09/18 10:27:52 −07:00 02238632: 85 01 01 |--|--|--secondaryRATType (1 byte) = 1 02238635: 30 21 |--|--SEQUENCE (33 bytes): 02238637: 81 02 02 a4 |--|--|--dataVolumeUplink (2 bytes) = 676 02238641: 82 02 02 d8 |--|--|--dataVolumeDownlink (2 bytes) = 728 02238645: 83 09 19 09 18 10 >|--|--|--rANStartTime (9 bytes) = 19/09/18 10:28:27 −07:00 02238656: 84 09 19 09 18 10 >|--|--|--rANEndTime (9 bytes) = 19/09/18 10:28:41 −07:00 02238667: 85 01 01 |--|--|--secondaryRATType (1 byte) = 1 02238670: 30 21 |--|--SEQUENCE (33 bytes): 02238672: 81 02 14 34 |--|--|--dataVolumeUplink (2 bytes) = 5172 02238676: 82 02 15 54 |--|--|--dataVolumeDownlink (2 bytes) = 5460 02238680: 83 09 19 09 18 10 >|--|--|--rANStartTime (9 bytes) = 19/09/18 10:29:09 −07:00 02238691: 84 09 19 09 18 10 >|--|--|--rANEndTime (9 bytes) = 19/09/18 10:30:27 −07:00 02238702: 85 01 01 |--|--|--secondaryRATType (1 byte) = 1 02238705: 30 21 |--|--SEQUENCE (33 bytes): 02238707: 81 02 00 90 |--|--|--dataVolumeUplink (2 bytes) = 144 02238711: 82 02 03 04 |--|--|--dataVolumeDownlink (2 bytes) = 772 02238715: 83 09 19 09 18 10 >|--|--|--rANStartTime (9 bytes) = 19/09/18 10:30:37 −07:00 02238726: 84 09 19 09 18 10 >|--|--|--rANEndTime (9 bytes) = 19/09/18 10:30:48 −07:00 02238737: 85 01 01 |--|--|--secondaryRATType (1 byte) = 1 . . . . .

As described above, by correlating the two entries based on the timeOfReport and rANEndTime values, it is possible to deduce the Service ID of the Secondary RAT usage on the PGW CDR.

Provided below in Table 1, for reference, are certain details of formatting for the “List of RAN Secondary RAT Usage Reports”.

TABLE 1 List of RAN Secondary RAT Usage Reports Description This list applies to SGW and PGW CDRs, and includes one or more containers reported from the RAN for a secondary RAT Applies to 5G NSA. ASN.1 Code bf40 (SGW) CSV bf49 (PGW) Length N/A Variable Format Data Volume Uplink Sequence: Data Volume Downlink Data Volume Uplink RAN Start Time Data Volume Downlink RAN End Time RAN Start Time Secondary RAT Type RAN End Time See TS 3GPP 32.298 Version Secondary RAT Type 15.2.0 for encoding details Example ‘250,100,1526580685,1526580745,1’ bf498187301f81011482011e83091805171406 452d040084091805171407452d0400850101

Referring now to an example of another embodiment, this comprises having the PGW insert additional fields in the basic service data indicating the uplink and downlink data usage on NR. This information would be inserted within the same container as overall data usage where the Service ID is currently included. It should be noted that this embodiment will change the format of all such modified PGW CDRs, including those where no NR data usage exists. As a result of that, billing systems and other back-office systems that receive the modified PGW CDRs will likely need to be updated in order to recognize the new fields in conjunction with introducing them in the PGW CDRs. Below is an example of this modified CDR embodiment, wherein this example includes the same NR usage (as the previous example) in the basic service data (see the two “New field” notations, which are shown in bold below). Note that certain values in the below example have been replaced with “- - - -” markings.

02237202: 30 4c |--|--SEQUENCE (76 bytes): 02237204: 81 04 01 60 00 80 |--|--|--ratingGroup (4 bytes) = 23068800 02237210: ---- |--|--|--chargingRuleBaseName (3 bytes) = “----” 02237215: 84 01 17 |--|--|--localSequenceNumber (1 byte) = 23 02237218: 85 09 19 09 18 10 >|--|--|--timeOfFirstUsage (9 bytes) = 19/09/18 10:29:07 −07:00 02237229: 86 09 19 09 18 10 >|--|--|--timeOfLastUsage (9 bytes) = 19/09/18 10:30:17 −07:00 02237240: 87 01 46 |--|--|--timeUsage (1 byte) = 70 02237243: 88 05 00 00 00 00 >|--|--|--serviceConditionChange (5 bytes) = 0000.0000 0000.0000 0000.0000 0000.0000 1000.0000 02237250: aa 06 |--|--|--sgsn-Address (6 bytes): 02237252: ---- |--|--|--iPBinV4Address (4 bytes) = ---- 02237258: 8c 02 15 b4 |--|--|--datavolumeFBCUplink (2 bytes) = 5556 02237262: 8d 02 16 fa |--|--|--datavolumeFBCDownlink (2 bytes) = 5882 New field |--|--|--NRdataVolumeUplink (2 bytes) = 5172 New field |--|--|--NRdataVolumeDownlink (2 bytes) = 5460 02237266: 8e 09 19 09 18 10 >--|--|--timeOfReport (9 bytes) = 19/09/18 10:30:27 −07:00 02237277: 91 01 01 |--|--|--serviceIdentifier (1 byte) = 1

While the above example shows each of the two new fields being two bytes, the size of each of the new fields could be any desired appropriate number of byte(s).

Referring now to FIG. 2B, various steps of a method 2100 according to an embodiment are shown. As seen in this FIG. 2B, step 2102 comprises obtaining a message associated with a 5th Generation (5G) wireless service, the message containing: a first section including a service type identifier entry and a first timestamp that corresponds to the service type identifier entry; and a second section including a secondary radio access technology (RAT) entry, one or more data volume entries, and a second timestamp that corresponds to the secondary RAT entry and to the one or more data volume entries. Next, step 2104 comprises matching the first timestamp and the second timestamp based upon a first value of the first timestamp equaling a second value of the second timestamp. Next, step 2106 comprises responsive to the matching of the first timestamp and the second timestamp, associating the service type identifier entry of the first section with the one or more data volume entries of the second section.

While for purposes of simplicity of explanation, the respective processes are shown and described as a series of blocks in FIG. 2B, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described herein.

Referring now to FIG. 2C, various steps of a method 2200 according to an embodiment are shown. As seen in this FIG. 2C, step 2202 comprises obtaining a charging data report (CDR) associated with a 5th Generation (5G) wireless service. Next, step 2204 comprises determining, from the CDR, a value of a first timestamp that corresponds to a service type identifier entry that is in a first portion of the CDR. Next, step 2206 comprises identifying, from the CDR, data volume information that is in a second portion of the CDR and that corresponds to a second timestamp having a second value that matches the first value of the first timestamp. Next, step 2208 comprises associating, based upon the second timestamp having the second value that matches the first value of the first timestamp, the service type identifier entry of the first portion of the CDR with the data volume information of the second portion of the CDR.

While for purposes of simplicity of explanation, the respective processes are shown and described as a series of blocks in FIG. 2C, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described herein.

Referring now to FIG. 2D, various steps of a method 2300 according to an embodiment are shown. As seen in this FIG. 2D, step 2302 comprises obtaining, by a processing system including a processor, first information indicative of an uplink data volume associated with a 5th Generation (5G) wireless service. Next, step 2304 comprises obtaining, by the processing system, second information indicative of a downlink data volume associated with the 5G wireless service. Next, step 2306 comprises generating, by the processing system, a charging data record (CDR), the generating comprising: inserting into a list of service data section of the CDR a first entry, the first entry being the first information indicative of the uplink data volume associated with the 5G wireless service; and inserting into the list of service data section of the CDR a second entry, the second entry being the second information indicative of the downlink data volume associated with the 5G wireless service.

While for purposes of simplicity of explanation, the respective processes are shown and described as a series of blocks in FIG. 2D, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described herein.

In various embodiments, one value of one timestamp (e.g., a first timestamp) equaling another value of another timestamp (e.g., a second timestamp) can mean the one value of the one timestamp being the same as the another value of the another timestamp.

In various embodiments, one value of one timestamp (e.g., a first timestamp) equaling another value of another timestamp (e.g., a second timestamp) can mean the one value of the one timestamp and the another value of the another timestamp being within a threshold differential of each other. For example, being within a certain time span of each another (such as being within one second of each other).

In various embodiments, having one value of one timestamp (e.g., a first timestamp) that matches another value of another timestamp (e.g., a second timestamp) can mean the one value of the one timestamp being the same as the another value of the another timestamp.

In various embodiments, having one value of one timestamp (e.g., a first timestamp) that matches another value of another timestamp (e.g., a second timestamp) can mean the one value of the one timestamp and the another value of the another timestamp being within a threshold differential of each other. For example, being within a certain time span of each another (such as being within one second of each other).

As described herein, various embodiments provide for billing (e.g., retail billing to wireless subscribers) in the context of 5G Option 3X Roaming.

As described herein, various embodiments provide for assigning a billing Service ID to data usage on a New Radio (NR) radio access network in a 5G Option 3X network.

As described herein, various embodiments facilitate secondary RAT usage data reporting in 5G Option 3X implementations.

As described herein, various embodiments can be implemented in the context of one or more different SGW and/or PGW vendors.

As described herein, each of SGW and PGW support secondary RAT data volume reporting per 3GPP 23.401.

As described herein, various embodiments can utilize NR data as Secondary RAT usage data for retail billing.

As described herein, various embodiments can apply service ID's to inform billing systems what type of data a respective mobile device is using so that the data usage can be differentiated.

As described herein, various embodiments can identify data which should be zero-rated versus billable usage to a respective subscriber.

Referring now to FIG. 3, a block diagram 300 is shown illustrating an example, non-limiting embodiment of a virtualized communication network in accordance with various aspects described herein. In particular a virtualized communication network is presented that can be used to implement some or all of the subsystems and functions of communication network 100, some or all of the subsystems and functions of network flow 200 and/or some or all of the functions of methods 2100, 2200 and/or 2300 presented in FIGS. 1, 2A, 2B, 2C, and 2D. For example, virtualized communication network 300 can facilitate in whole or in part message processing (e.g., CDR processing), message post-processing (e.g., CDR post-processing), message creation (e.g., CDR creation) and/or billing that is related to wireless frequency usage.

In particular, a cloud networking architecture is shown that leverages cloud technologies and supports rapid innovation and scalability via a transport layer 350, a virtualized network function cloud 325 and/or one or more cloud computing environments 375. In various embodiments, this cloud networking architecture is an open architecture that leverages application programming interfaces (APIs); reduces complexity from services and operations; supports more nimble business models; and rapidly and seamlessly scales to meet evolving customer requirements including traffic growth, diversity of traffic types, and diversity of performance and reliability expectations.

In contrast to traditional network elements—which are typically integrated to perform a single function, the virtualized communication network employs virtual network elements (VNEs) 330, 332, 334, etc. that perform some or all of the functions of network elements 150, 152, 154, 156, etc. For example, the network architecture can provide a substrate of networking capability, often called Network Function Virtualization Infrastructure (NFVI) or simply infrastructure that is capable of being directed with software and Software Defined Networking (SDN) protocols to perform a broad variety of network functions and services. This infrastructure can include several types of substrates. The most typical type of substrate being servers that support Network Function Virtualization (NFV), followed by packet forwarding capabilities based on generic computing resources, with specialized network technologies brought to bear when general purpose processors or general purpose integrated circuit devices offered by merchants (referred to herein as merchant silicon) are not appropriate. In this case, communication services can be implemented as cloud-centric workloads.

As an example, a traditional network element 150 (shown in FIG. 1), such as an edge router can be implemented via a VNE 330 composed of NFV software modules, merchant silicon, and associated controllers. The software can be written so that increasing workload consumes incremental resources from a common resource pool, and moreover so that it's elastic: so the resources are only consumed when needed. In a similar fashion, other network elements such as other routers, switches, edge caches, and middle-boxes are instantiated from the common resource pool. Such sharing of infrastructure across a broad set of uses makes planning and growing infrastructure easier to manage.

In an embodiment, the transport layer 350 includes fiber, cable, wired and/or wireless transport elements, network elements and interfaces to provide broadband access 110, wireless access 120, voice access 130, media access 140 and/or access to content sources 175 for distribution of content to any or all of the access technologies. In particular, in some cases a network element needs to be positioned at a specific place, and this allows for less sharing of common infrastructure. Other times, the network elements have specific physical layer adapters that cannot be abstracted or virtualized, and might require special DSP code and analog front-ends (AFEs) that do not lend themselves to implementation as VNEs 330, 332 or 334. These network elements can be included in transport layer 350.

The virtualized network function cloud 325 interfaces with the transport layer 350 to provide the VNEs 330, 332, 334, etc. to provide specific NFVs. In particular, the virtualized network function cloud 325 leverages cloud operations, applications, and architectures to support networking workloads. The virtualized network elements 330, 332 and 334 can employ network function software that provides either a one-for-one mapping of traditional network element function or alternately some combination of network functions designed for cloud computing. For example, VNEs 330, 332 and 334 can include route reflectors, domain name system (DNS) servers, and dynamic host configuration protocol (DHCP) servers, system architecture evolution (SAE) and/or mobility management entity (MME) gateways, broadband network gateways, IP edge routers for IP-VPN, Ethernet and other services, load balancers, distributers and other network elements. Because these elements don't typically need to forward large amounts of traffic, their workload can be distributed across a number of servers—each of which adds a portion of the capability, and overall which creates an elastic function with higher availability than its former monolithic version. These virtual network elements 330, 332, 334, etc. can be instantiated and managed using an orchestration approach similar to those used in cloud compute services.

The cloud computing environments 375 can interface with the virtualized network function cloud 325 via APIs that expose functional capabilities of the VNEs 330, 332, 334, etc. to provide the flexible and expanded capabilities to the virtualized network function cloud 325. In particular, network workloads may have applications distributed across the virtualized network function cloud 325 and cloud computing environment 375 and in the commercial cloud, or might simply orchestrate workloads supported entirely in NFV infrastructure from these third party locations.

Turning now to FIG. 4, there is illustrated a block diagram of a computing environment in accordance with various aspects described herein. In order to provide additional context for various embodiments of the embodiments described herein, FIG. 4 and the following discussion are intended to provide a brief, general description of a suitable computing environment 400 in which the various embodiments of the subject disclosure can be implemented. In particular, computing environment 400 can be used in the implementation of network elements 150, 152, 154, 156, access terminal 112, base station or access point 122, switching device 132, media terminal 142, and/or VNEs 330, 332, 334, etc. Each of these devices can be implemented via computer-executable instructions that can run on one or more computers, and/or in combination with other program modules and/or as a combination of hardware and software. For example, computing environment 400 can facilitate in whole or in part message processing (e.g., CDR processing), message post-processing (e.g., CDR post-processing), message creation (e.g., CDR creation) and/or billing that is related to wireless frequency usage.

Generally, program modules comprise routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the methods can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.

As used herein, a processing circuit includes one or more processors as well as other application specific circuits such as an application specific integrated circuit, digital logic circuit, state machine, programmable gate array or other circuit that processes input signals or data and that produces output signals or data in response thereto. It should be noted that while any functions and features described herein in association with the operation of a processor could likewise be performed by a processing circuit.

The illustrated embodiments of the embodiments herein can be also practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

Computing devices typically comprise a variety of media, which can comprise computer-readable storage media and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable storage media can be any available storage media that can be accessed by the computer and comprises both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable instructions, program modules, structured data or unstructured data.

Computer-readable storage media can comprise, but are not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or other tangible and/or non-transitory media which can be used to store desired information. In this regard, the terms “tangible” or “non-transitory” herein as applied to storage, memory or computer-readable media, are to be understood to exclude only propagating transitory signals per se as modifiers and do not relinquish rights to all standard storage, memory or computer-readable media that are not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.

Communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and comprises any information delivery or transport media. The term “modulated data signal” or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media comprise wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 4, the example environment can comprise a computer 402, the computer 402 comprising a processing unit 404, a system memory 406 and a system bus 408. The system bus 408 couples system components including, but not limited to, the system memory 406 to the processing unit 404. The processing unit 404 can be any of various commercially available processors. Dual microprocessors and other multiprocessor architectures can also be employed as the processing unit 404.

The system bus 408 can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 406 comprises ROM 410 and RAM 412. A basic input/output system (BIOS) can be stored in a non-volatile memory such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer 402, such as during startup. The RAM 412 can also comprise a high-speed RAM such as static RAM for caching data.

The computer 402 further comprises an internal hard disk drive (HDD) 414 (e.g., EIDE, SATA), which internal HDD 414 can also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD) 416, (e.g., to read from or write to a removable diskette 418) and an optical disk drive 420, (e.g., reading a CD-ROM disk 422 or, to read from or write to other high capacity optical media such as the DVD). The HDD 414, magnetic FDD 416 and optical disk drive 420 can be connected to the system bus 408 by a hard disk drive interface 424, a magnetic disk drive interface 426 and an optical drive interface 428, respectively. The hard disk drive interface 424 for external drive implementations comprises at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.

The drives and their associated computer-readable storage media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer 402, the drives and storage media accommodate the storage of any data in a suitable digital format. Although the description of computer-readable storage media above refers to a hard disk drive (HDD), a removable magnetic diskette, and a removable optical media such as a CD or DVD, it should be appreciated by those skilled in the art that other types of storage media which are readable by a computer, such as zip drives, magnetic cassettes, flash memory cards, cartridges, and the like, can also be used in the example operating environment, and further, that any such storage media can contain computer-executable instructions for performing the methods described herein.

A number of program modules can be stored in the drives and RAM 412, comprising an operating system 430, one or more application programs 432, other program modules 434 and program data 436. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM 412. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.

A user can enter commands and information into the computer 402 through one or more wired/wireless input devices, e.g., a keyboard 438 and a pointing device, such as a mouse 440. Other input devices (not shown) can comprise a microphone, an infrared (IR) remote control, a joystick, a game pad, a stylus pen, touch screen or the like. These and other input devices are often connected to the processing unit 404 through an input device interface 442 that can be coupled to the system bus 408, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a universal serial bus (USB) port, an IR interface, etc.

A monitor 444 or other type of display device can be also connected to the system bus 408 via an interface, such as a video adapter 446. It will also be appreciated that in alternative embodiments, a monitor 444 can also be any display device (e.g., another computer having a display, a smart phone, a tablet computer, etc.) for receiving display information associated with computer 402 via any communication means, including via the Internet and cloud-based networks. In addition to the monitor 444, a computer typically comprises other peripheral output devices (not shown), such as speakers, printers, etc.

The computer 402 can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s) 448. The remote computer(s) 448 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically comprises many or all of the elements described relative to the computer 402, although, for purposes of brevity, only a remote memory/storage device 450 is illustrated. The logical connections depicted comprise wired/wireless connectivity to a local area network (LAN) 452 and/or larger networks, e.g., a wide area network (WAN) 454. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 402 can be connected to the LAN 452 through a wired and/or wireless communication network interface or adapter 456. The adapter 456 can facilitate wired or wireless communication to the LAN 452, which can also comprise a wireless AP disposed thereon for communicating with the adapter 456.

When used in a WAN networking environment, the computer 402 can comprise a modem 458 or can be connected to a communications server on the WAN 454 or has other means for establishing communications over the WAN 454, such as by way of the Internet. The modem 458, which can be internal or external and a wired or wireless device, can be connected to the system bus 408 via the input device interface 442. In a networked environment, program modules depicted relative to the computer 402 or portions thereof, can be stored in the remote memory/storage device 450. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

The computer 402 can be operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone. This can comprise Wireless Fidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.

Wi-Fi can allow connection to the Internet from a couch at home, a bed in a hotel room or a conference room at work, without wires. Wi-Fi is a wireless technology similar to that used in a cell phone that enables such devices, e.g., computers, to send and receive data indoors and out; anywhere within the range of a base station. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b, g, n, ac, ag, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wired networks (which can use IEEE 802.3 or Ethernet). Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands for example or with products that contain both bands (dual band), so the networks can provide real-world performance similar to the basic 10BaseT wired Ethernet networks used in many offices.

Turning now to FIG. 5, an embodiment 500 of a mobile network platform 510 is shown that is an example of network elements 150, 152, 154, 156, and/or VNEs 330, 332, 334, etc. For example, platform 510 can facilitate in whole or in part message processing (e.g., CDR processing), message post-processing (e.g., CDR post-processing), message creation (e.g., CDR creation) and/or billing that is related to wireless frequency usage. In one or more embodiments, the mobile network platform 510 can generate and receive signals transmitted and received by base stations or access points such as base station or access point 122. Generally, mobile network platform 510 can comprise components, e.g., nodes, gateways, interfaces, servers, or disparate platforms, that facilitate both packet-switched (PS) (e.g., internet protocol (IP), frame relay, asynchronous transfer mode (ATM)) and circuit-switched (CS) traffic (e.g., voice and data), as well as control generation for networked wireless telecommunication. As a non-limiting example, mobile network platform 510 can be included in telecommunications carrier networks, and can be considered carrier-side components as discussed elsewhere herein. Mobile network platform 510 comprises CS gateway node(s) 512 which can interface CS traffic received from legacy networks like telephony network(s) 540 (e.g., public switched telephone network (PSTN), or public land mobile network (PLMN)) or a signaling system #7 (SS7) network 560. CS gateway node(s) 512 can authorize and authenticate traffic (e.g., voice) arising from such networks. Additionally, CS gateway node(s) 512 can access mobility, or roaming, data generated through SS7 network 560; for instance, mobility data stored in a visited location register (VLR), which can reside in memory 530. Moreover, CS gateway node(s) 512 interfaces CS-based traffic and signaling and PS gateway node(s) 518. As an example, in a 3GPP UMTS network, CS gateway node(s) 512 can be realized at least in part in gateway GPRS support node(s) (GGSN). It should be appreciated that functionality and specific operation of CS gateway node(s) 512, PS gateway node(s) 518, and serving node(s) 516, is provided and dictated by radio technology(ies) utilized by mobile network platform 510 for telecommunication over a radio access network 520 with other devices, such as a radiotelephone 575.

In addition to receiving and processing CS-switched traffic and signaling, PS gateway node(s) 518 can authorize and authenticate PS-based data sessions with served mobile devices. Data sessions can comprise traffic, or content(s), exchanged with networks external to the mobile network platform 510, like wide area network(s) (WANs) 550, enterprise network(s) 570, and service network(s) 580, which can be embodied in local area network(s) (LANs), can also be interfaced with mobile network platform 510 through PS gateway node(s) 518. It is to be noted that WANs 550 and enterprise network(s) 570 can embody, at least in part, a service network(s) like IP multimedia subsystem (IMS). Based on radio technology layer(s) available in technology resource(s) or radio access network 520, PS gateway node(s) 518 can generate packet data protocol contexts when a data session is established; other data structures that facilitate routing of packetized data also can be generated. To that end, in an aspect, PS gateway node(s) 518 can comprise a tunnel interface (e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (not shown)) which can facilitate packetized communication with disparate wireless network(s), such as Wi-Fi networks.

In embodiment 500, mobile network platform 510 also comprises serving node(s) 516 that, based upon available radio technology layer(s) within technology resource(s) in the radio access network 520, convey the various packetized flows of data streams received through PS gateway node(s) 518. It is to be noted that for technology resource(s) that rely primarily on CS communication, server node(s) can deliver traffic without reliance on PS gateway node(s) 518; for example, server node(s) can embody at least in part a mobile switching center. As an example, in a 3GPP UMTS network, serving node(s) 516 can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s) 514 in mobile network platform 510 can execute numerous applications that can generate multiple disparate packetized data streams or flows, and manage (e.g., schedule, queue, format . . . ) such flows. Such application(s) can comprise add-on features to standard services (for example, provisioning, billing, customer support . . . ) provided by mobile network platform 510. Data streams (e.g., content(s) that are part of a voice call or data session) can be conveyed to PS gateway node(s) 518 for authorization/authentication and initiation of a data session, and to serving node(s) 516 for communication thereafter. In addition to application server, server(s) 514 can comprise utility server(s), a utility server can comprise a provisioning server, an operations and maintenance server, a security server that can implement at least in part a certificate authority and firewalls as well as other security mechanisms, and the like. In an aspect, security server(s) secure communication served through mobile network platform 510 to ensure network's operation and data integrity in addition to authorization and authentication procedures that CS gateway node(s) 512 and PS gateway node(s) 518 can enact. Moreover, provisioning server(s) can provision services from external network(s) like networks operated by a disparate service provider; for instance, WAN 550 or Global Positioning System (GPS) network(s) (not shown). Provisioning server(s) can also provision coverage through networks associated to mobile network platform 510 (e.g., deployed and operated by the same service provider), such as the distributed antennas networks shown in FIG. 1(s) that enhance wireless service coverage by providing more network coverage.

It is to be noted that server(s) 514 can comprise one or more processors configured to confer at least in part the functionality of mobile network platform 510. To that end, the one or more processor can execute code instructions stored in memory 530, for example. It is should be appreciated that server(s) 514 can comprise a content manager, which operates in substantially the same manner as described hereinbefore.

In example embodiment 500, memory 530 can store information related to operation of mobile network platform 510. Other operational information can comprise provisioning information of mobile devices served through mobile network platform 510, subscriber databases; application intelligence, pricing schemes, e.g., promotional rates, flat-rate programs, couponing campaigns; technical specification(s) consistent with telecommunication protocols for operation of disparate radio, or wireless, technology layers; and so forth. Memory 530 can also store information from at least one of telephony network(s) 540, WAN 550, SS7 network 560, or enterprise network(s) 570. In an aspect, memory 530 can be, for example, accessed as part of a data store component or as a remotely connected memory store.

In order to provide a context for the various aspects of the disclosed subject matter, FIG. 5, and the following discussion, are intended to provide a brief, general description of a suitable environment in which the various aspects of the disclosed subject matter can be implemented. While the subject matter has been described above in the general context of computer-executable instructions of a computer program that runs on a computer and/or computers, those skilled in the art will recognize that the disclosed subject matter also can be implemented in combination with other program modules. Generally, program modules comprise routines, programs, components, data structures, etc. that perform particular tasks and/or implement particular abstract data types.

Turning now to FIG. 6, an illustrative embodiment of a communication device 600 is shown. The communication device 600 can serve as an illustrative embodiment of devices such as data terminals 114, mobile devices 124, vehicle 126, display devices 144 or other client devices for communication via either communications network 125. For example, computing device 600 can facilitate in whole or in part message processing (e.g., CDR processing), message post-processing (e.g., CDR post-processing), message creation (e.g., CDR creation) and/or billing that is related to wireless frequency usage.

The communication device 600 can comprise a wireline and/or wireless transceiver 602 (herein transceiver 602), a user interface (UI) 604, a power supply 614, a location receiver 616, a motion sensor 618, an orientation sensor 620, and a controller 606 for managing operations thereof. The transceiver 602 can support short-range or long-range wireless access technologies such as Bluetooth®, ZigBee®, WiFi, DECT, or cellular communication technologies, just to mention a few (Bluetooth® and ZigBee® are trademarks registered by the Bluetooth® Special Interest Group and the ZigBee® Alliance, respectively). Cellular technologies can include, for example, CDMA-1×, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO, WiMAX, SDR, LTE, as well as other next generation wireless communication technologies as they arise. The transceiver 602 can also be adapted to support circuit-switched wireline access technologies (such as PSTN), packet-switched wireline access technologies (such as TCP/IP, VoIP, etc.), and combinations thereof.

The UI 604 can include a depressible or touch-sensitive keypad 608 with a navigation mechanism such as a roller ball, a joystick, a mouse, or a navigation disk for manipulating operations of the communication device 600. The keypad 608 can be an integral part of a housing assembly of the communication device 600 or an independent device operably coupled thereto by a tethered wireline interface (such as a USB cable) or a wireless interface supporting for example Bluetooth®. The keypad 608 can represent a numeric keypad commonly used by phones, and/or a QWERTY keypad with alphanumeric keys. The UI 604 can further include a display 610 such as monochrome or color LCD (Liquid Crystal Display), OLED (Organic Light Emitting Diode) or other suitable display technology for conveying images to an end user of the communication device 600. In an embodiment where the display 610 is touch-sensitive, a portion or all of the keypad 608 can be presented by way of the display 610 with navigation features.

The display 610 can use touch screen technology to also serve as a user interface for detecting user input. As a touch screen display, the communication device 600 can be adapted to present a user interface having graphical user interface (GUI) elements that can be selected by a user with a touch of a finger. The display 610 can be equipped with capacitive, resistive or other forms of sensing technology to detect how much surface area of a user's finger has been placed on a portion of the touch screen display. This sensing information can be used to control the manipulation of the GUI elements or other functions of the user interface. The display 610 can be an integral part of the housing assembly of the communication device 600 or an independent device communicatively coupled thereto by a tethered wireline interface (such as a cable) or a wireless interface.

The UI 604 can also include an audio system 612 that utilizes audio technology for conveying low volume audio (such as audio heard in proximity of a human ear) and high volume audio (such as speakerphone for hands free operation). The audio system 612 can further include a microphone for receiving audible signals of an end user. The audio system 612 can also be used for voice recognition applications. The UI 604 can further include an image sensor 613 such as a charged coupled device (CCD) camera for capturing still or moving images.

The power supply 614 can utilize common power management technologies such as replaceable and rechargeable batteries, supply regulation technologies, and/or charging system technologies for supplying energy to the components of the communication device 600 to facilitate long-range or short-range portable communications. Alternatively, or in combination, the charging system can utilize external power sources such as DC power supplied over a physical interface such as a USB port or other suitable tethering technologies.

The location receiver 616 can utilize location technology such as a global positioning system (GPS) receiver capable of assisted GPS for identifying a location of the communication device 600 based on signals generated by a constellation of GPS satellites, which can be used for facilitating location services such as navigation. The motion sensor 618 can utilize motion sensing technology such as an accelerometer, a gyroscope, or other suitable motion sensing technology to detect motion of the communication device 600 in three-dimensional space. The orientation sensor 620 can utilize orientation sensing technology such as a magnetometer to detect the orientation of the communication device 600 (north, south, west, and east, as well as combined orientations in degrees, minutes, or other suitable orientation metrics).

The communication device 600 can use the transceiver 602 to also determine a proximity to a cellular, WiFi, Bluetooth®, or other wireless access points by sensing techniques such as utilizing a received signal strength indicator (RSSI) and/or signal time of arrival (TOA) or time of flight (TOF) measurements. The controller 606 can utilize computing technologies such as a microprocessor, a digital signal processor (DSP), programmable gate arrays, application specific integrated circuits, and/or a video processor with associated storage memory such as Flash, ROM, RAM, SRAM, DRAM or other storage technologies for executing computer instructions, controlling, and processing data supplied by the aforementioned components of the communication device 600.

Other components not shown in FIG. 6 can be used in one or more embodiments of the subject disclosure. For instance, the communication device 600 can include a slot for adding or removing an identity module such as a Subscriber Identity Module (SIM) card or Universal Integrated Circuit Card (UICC). SIM or UICC cards can be used for identifying subscriber services, executing programs, storing subscriber data, and so on.

The terms “first,” “second,” “third,” and so forth, as used in the claims, unless otherwise clear by context, is for clarity only and doesn't otherwise indicate or imply any order in time. For instance, “a first determination,” “a second determination,” and “a third determination,” does not indicate or imply that the first determination is to be made before the second determination, or vice versa, etc.

In the subject specification, terms such as “store,” “storage,” “data store,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components described herein can be either volatile memory or nonvolatile memory, or can comprise both volatile and nonvolatile memory, by way of illustration, and not limitation, volatile memory, non-volatile memory, disk storage, and memory storage. Further, nonvolatile memory can be included in read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can comprise random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). Additionally, the disclosed memory components of systems or methods herein are intended to comprise, without being limited to comprising, these and any other suitable types of memory.

Moreover, it will be noted that the disclosed subject matter can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, mini-computing devices, mainframe computers, as well as personal computers, hand-held computing devices (e.g., PDA, phone, smartphone, watch, tablet computers, netbook computers, etc.), microprocessor-based or programmable consumer or industrial electronics, and the like. The illustrated aspects can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network; however, some if not all aspects of the subject disclosure can be practiced on stand-alone computers. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

In one or more embodiments, information regarding use of services can be generated including services being accessed, media consumption history, user preferences, and so forth. This information can be obtained by various methods including user input, detecting types of communications (e.g., video content vs. audio content), analysis of content streams, sampling, and so forth. The generating, obtaining and/or monitoring of this information can be responsive to an authorization provided by the user. In one or more embodiments, an analysis of data can be subject to authorization from user(s) associated with the data, such as an opt-in, an opt-out, acknowledgement requirements, notifications, selective authorization based on types of data, and so forth.

Some of the embodiments described herein can also employ artificial intelligence (AI) to facilitate automating one or more features described herein. The embodiments (e.g., in connection with automatically performing message processing (e.g., CDR processing), automatically performing message post-processing (e.g., CDR post-processing), automatically performing message creation (e.g., CDR creation) and/or automatically performing billing that is related to wireless frequency usage) can employ various AI-based schemes for carrying out various embodiments thereof. Moreover, the classifier can be employed to determine a ranking or priority of each message (e.g., CDR) and/or of each frequency (or frequency range). A classifier is a function that maps an input attribute vector, x=(x1, x2, x3, x4, . . . , xn), to a confidence that the input belongs to a class, that is, f(x)=confidence (class). Such classification can employ a probabilistic and/or statistical-based analysis (e.g., factoring into the analysis utilities and costs) to determine or infer an action that a user desires to be automatically performed. A support vector machine (SVM) is an example of a classifier that can be employed. The SVM operates by finding a hypersurface in the space of possible inputs, which the hypersurface attempts to split the triggering criteria from the non-triggering events. Intuitively, this makes the classification correct for testing data that is near, but not identical to training data. Other directed and undirected model classification approaches comprise, e.g., naïve Bayes, Bayesian networks, decision trees, neural networks, fuzzy logic models, and probabilistic classification models providing different patterns of independence can be employed. Classification as used herein also is inclusive of statistical regression that is utilized to develop models of priority.

As will be readily appreciated, one or more of the embodiments can employ classifiers that are explicitly trained (e.g., via a generic training data) as well as implicitly trained (e.g., via observing UE behavior, operator preferences, historical information, receiving extrinsic information). For example, SVMs can be configured via a learning or training phase within a classifier constructor and feature selection module. Thus, the classifier(s) can be used to automatically learn and perform a number of functions, including but not limited to determining according to predetermined criteria which of the one or more messages (e.g., one or more CDRs) to operate on and/or which frequency (or frequencies, or range of frequencies) to operate on.

As used in some contexts in this application, in some embodiments, the terms “component,” “system” and the like are intended to refer to, or comprise, a computer-related entity or an entity related to an operational apparatus with one or more specific functionalities, wherein the entity can be either hardware, a combination of hardware and software, software, or software in execution. As an example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, computer-executable instructions, a program, and/or a computer. By way of illustration and not limitation, both an application running on a server and the server can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, which is operated by a software or firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can comprise a processor therein to execute software or firmware that confers at least in part the functionality of the electronic components. While various components have been illustrated as separate components, it will be appreciated that multiple components can be implemented as a single component, or a single component can be implemented as multiple components, without departing from example embodiments.

Further, the various embodiments can be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device or computer-readable storage/communications media. For example, computer readable storage media can include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., compact disk (CD), digital versatile disk (DVD)), smart cards, and flash memory devices (e.g., card, stick, key drive). Of course, those skilled in the art will recognize many modifications can be made to this configuration without departing from the scope or spirit of the various embodiments.

In addition, the words “example” and “exemplary” are used herein to mean serving as an instance or illustration. Any embodiment or design described herein as “example” or “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word example or exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.

Moreover, terms such as “user equipment,” “mobile station,” “mobile,” subscriber station,” “access terminal,” “terminal,” “handset,” “mobile device” (and/or terms representing similar terminology) can refer to a wireless device utilized by a subscriber or user of a wireless communication service to receive or convey data, control, voice, video, sound, gaming or substantially any data-stream or signaling-stream. The foregoing terms are utilized interchangeably herein and with reference to the related drawings.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer” and the like are employed interchangeably throughout, unless context warrants particular distinctions among the terms. It should be appreciated that such terms can refer to human entities or automated components supported through artificial intelligence (e.g., a capacity to make inference based, at least, on complex mathematical formalisms), which can provide simulated vision, sound recognition and so forth.

As employed herein, the term “processor” can refer to substantially any computing processing unit or device comprising, but not limited to comprising, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology; parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can refer to an integrated circuit, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic controller (PLC), a complex programmable logic device (CPLD), a discrete gate or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of user equipment. A processor can also be implemented as a combination of computing processing units.

As used herein, terms such as “data storage,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components or computer-readable storage media, described herein can be either volatile memory or nonvolatile memory or can include both volatile and nonvolatile memory.

What has been described above includes mere examples of various embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing these examples, but one of ordinary skill in the art can recognize that many further combinations and permutations of the present embodiments are possible. Accordingly, the embodiments disclosed and/or claimed herein are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.

In addition, a flow diagram may include a “start” and/or “continue” indication. The “start” and “continue” indications reflect that the steps presented can optionally be incorporated in or otherwise used in conjunction with other routines. In this context, “start” indicates the beginning of the first step presented and may be preceded by other activities not specifically shown. Further, the “continue” indication reflects that the steps presented may be performed multiple times and/or may be succeeded by other activities not specifically shown. Further, while a flow diagram indicates a particular ordering of steps, other orderings are likewise possible provided that the principles of causality are maintained.

As may also be used herein, the term(s) “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via one or more intervening items. Such items and intervening items include, but are not limited to, junctions, communication paths, components, circuit elements, circuits, functional blocks, and/or devices. As an example of indirect coupling, a signal conveyed from a first item to a second item may be modified by one or more intervening items by modifying the form, nature or format of information in a signal, while one or more elements of the information in the signal are nevertheless conveyed in a manner than can be recognized by the second item. In a further example of indirect coupling, an action in a first item can cause a reaction on the second item, as a result of actions and/or reactions in one or more intervening items.

Although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement which achieves the same or similar purpose may be substituted for the embodiments described or shown by the subject disclosure. The subject disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, can be used in the subject disclosure. For instance, one or more features from one or more embodiments can be combined with one or more features of one or more other embodiments. In one or more embodiments, features that are positively recited can also be negatively recited and excluded from the embodiment with or without replacement by another structural and/or functional feature. The steps or functions described with respect to the embodiments of the subject disclosure can be performed in any order. The steps or functions described with respect to the embodiments of the subject disclosure can be performed alone or in combination with other steps or functions of the subject disclosure, as well as from other embodiments or from other steps that have not been described in the subject disclosure. Further, more than or less than all of the features described with respect to an embodiment can also be utilized. 

1. A device, comprising: a processing system including a processor; and a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations, the operations comprising: obtaining a message associated with a 5th Generation (5G) wireless service, the message containing: a first section including a service type identifier entry and a first timestamp that corresponds to the service type identifier entry; and a second section including a secondary radio access technology (RAT) entry, one or more data volume entries, and a second timestamp that corresponds to the secondary RAT entry and to the one or more data volume entries; matching the first timestamp and the second timestamp based upon a first value of the first timestamp equaling a second value of the second timestamp; and responsive to the matching of the first timestamp and the second timestamp, associating the service type identifier entry of the first section with the one or more data volume entries of the second section.
 2. The device of claim 1, wherein the message comprises a charging data record (CDR) from a packet data network gateway (PGW).
 3. The device of claim 2, wherein the message conforms to a 3GPP 23.401 standard.
 4. The device of claim 1, wherein the operations further comprise billing a subscriber to the 5G wireless service based at least in part upon the service type identifier entry of the first section that is associated with the one or more data volume entries of the second section.
 5. The device of claim 1, wherein the first section comprises a list of service data section and wherein the second section comprises a list of radio access network (RAN) secondary RAT usage reports section.
 6. The device of claim 1, wherein the service type identifier entry distinguishes between use of the 5G wireless service and use of a prior generation wireless service.
 7. The device of claim 1, wherein the service type identifier entry distinguishes between use of a first type of the 5G wireless service and use of a second type of the 5G wireless service.
 8. The device of claim 1, wherein the one or more data volume entries is a single data volume entry that corresponds to one of an uplink data volume or a downlink data volume.
 9. The device of claim 1, wherein the one or more data volume entries comprises: a first data volume entry that corresponds to uplink data volume; and a second data volume entry that corresponds to downlink data volume.
 10. The device of claim 9, wherein each of the uplink data volume and the downlink data volume is associated with a 5G communication.
 11. The device of claim 1, wherein the first value of the first timestamp equaling the second value of the second timestamp comprises the first value of the first timestamp being within a temporal threshold of the second timestamp.
 12. The device of claim 11, wherein the temporal threshold is one second. 13-20. (canceled)
 21. A non-transitory, machine-readable medium, comprising executable instructions that, when executed by a processing system including a processor, facilitate performance of operations, the operations comprising: obtaining a message associated with a 5th Generation (5G) wireless service, the message containing: a first section including a service type identifier entry and a first timestamp that corresponds to the service type identifier entry; and a second section including a secondary radio access technology (RAT) entry, one or more data volume entries, and a second timestamp that corresponds to the secondary RAT entry and to the one or more data volume entries; matching the first timestamp and the second timestamp based upon a first value of the first timestamp equaling a second value of the second timestamp; and responsive to the matching of the first timestamp and the second timestamp, associating the service type identifier entry of the first section with the one or more data volume entries of the second section.
 22. The non-transitory, machine readable medium of claim 21, wherein the message comprises a charging data record (CDR) from a packet data network gateway (PGW).
 23. The non-transitory, machine readable medium of claim 22, wherein the message conforms to a 3GPP 23.401 standard.
 24. The non-transitory, machine readable medium of claim 21, wherein the operations further comprise billing a subscriber to the 5G wireless service based at least in part upon the service type identifier entry of the first section that is associated with the one or more data volume entries of the second section.
 25. A method comprising: obtaining, by a processing system including a processor, a message associated with a 5th Generation (5G) wireless service, the message containing: a first section including a service type identifier entry and a first timestamp that corresponds to the service type identifier entry; and a second section including a secondary radio access technology (RAT) entry, one or more data volume entries, and a second timestamp that corresponds to the secondary RAT entry and to the one or more data volume entries; matching, by the processing system, the first timestamp and the second timestamp based upon a first value of the first timestamp equaling a second value of the second timestamp; and responsive to the matching of the first timestamp and the second timestamp, associating, by the processing system, the service type identifier entry of the first section with the one or more data volume entries of the second section.
 26. The method of claim 25, wherein the first section comprises a list of service data section and wherein the second section comprises a list of radio access network (RAN) secondary RAT usage reports section.
 27. The method of claim 25, wherein the service type identifier entry distinguishes between use of the 5G wireless service and use of a prior generation wireless service.
 28. The method of claim 25, wherein the service type identifier entry distinguishes between use of a first type of the 5G wireless service and use of a second type of the 5G wireless service. 